This forum is closed to new posts and
responses. Individual names altered for privacy purposes. The information contained in this website is provided for informational purposes only and should not be construed as a forum for customer support requests. Any customer support requests should be directed to the official HCL customer support channels below:
I think those errors occurs mostly with another program trying to locally access the files. Backup programs that are not Notes friendly can keep their locks on the files and when the Notes Servers need to process, the OS usually blocks another program from accessing.
I think the following happened to me once. Another thing to watch for is LotusScript agents that try to open databases as if they were "local" and the Notes server already has those files open--because AGMR is running the agent. (If you are not getting any data loss, I suspect this is happening.) Try to get your LotusScript agents that run on the server specify the servername in the code when needed.
The most offending code is when a LotusScript agent tries to access another database. Developers code as it was a "" or local database; however, when running scheduled on the server, the agent will attempt to get local access while the server has access. Hence the error.
To fix it, speicify the severname when using GetDatabase in LotusScript by hardcoding it or by getting the servername by the NotesSession.Servername.
To find this error, I would look at the lines right before your error message to see which agent that AMGR attempted to start to run.
-Kyle Huang
Feedback response number WEBB8GSSLQ created by ~John Reniskiikle on 05/12/2011